Method and Apparatus for Controlling Data Transmission in a Communication System

ABSTRACT

A method and apparatus for controlling data transmission in a communication system is provided. In one aspect of the invention relates to a method performed by a data transmission control node in a communication system. The method comprises receiving a request for a transmission rule for a device; determining a transmission impacting parameter for the device based on information received in the request and based on the transmission impacting parameter further determining a device transmission rule governing the data transmission by the device. A transmission rule deployment message is transmitted to the device enabling the device to govern transmission in accordance with the device transmission rule. Another aspect of the invention relates to a transmission control node apparatus and a further aspect relates to a user equipment device. An advantage is that enabling a sending device to optimize its traffic allows a better performing network with higher utilization.

FIELD OF INVENTION

The present invention relates to a method and apparatus for controllingdata transmission in a communication system.

BACKGROUND

Operators of communication networks face a challenge in how to securemobile broadband revenues.

The tremendous uptake in mobile broadband subscribers and data volumewill require substantial investments in operators' telecominfrastructure. On the other hand, users will expect their operator todeliver the service experience they have paid for. Thus, operatorrevenues from mobile broadband rely on satisfied customers.

A small fraction of the users generates traffic exceeding those ofnormal users with magnitude. In many networks, these heavy users areconsuming a quite large part of today's network resources. Experienceshows that heavy users normally constitutes of 5-10% of the totalsubscribers, but could consume 70-85% of the network resources. It hasbeen shown that often the heavy users are the biggest consumers of thenetwork resources also during busy hour.

With policy control operators can distribute the traffic load moreevenly, giving a defined Quality of Service QoS, e.g. more bandwidthresources, for the normal users (the majority of the subscribers),particularly during the busy hour. Policy control also enables operatorsto push the heavy user's traffic into the non-busy hours where number ofnormal users is lower. For some heavy user applications, time of day isnot very critical since they click to download and leave the applicationrunning for hours or even days before completing a larger download.Policy control therefore helps controlling network capacity utilizationby managing the traffic in a smarter way.

Today and in the future, operators are introducing new premium services,for example ring tones download, TV, video streaming, VoIP, etc. To makesure that the subscribers get the best end user experience whileconsuming these premium services policy control is used to allocate morebandwidth for these applications when being accessed.

Operators use policy control to move away from a blanket, flat fee foreveryone, to the right price for the right service at the right timeensuring users get the user experience paid for. This gives consumersthe chance to choose a subscription that best meets their circumstancesand decide how to act when the subscription doesn't meet their current,specific needs.

For operators, policy control makes it possible to get the most valuefrom their bandwidth, by leveraging the right price for the rightservice at the right time.

In order to handle policy control and charging, the 3rd GenerationPartnership Project 3GPP has in TS 23.203 V10.4.0 (2011-06) specified apolicy and charging control PCC functionality encompassing the two mainfunctions:

-   -   Policy control (e.g. gating control, QoS control, QoS signaling,        etc.);    -   Flow Based Charging, including charging control and online        credit control.

The PCC functionality is comprised by the functions of the Policy andCharging Enforcement Function PCEF, the Bearer Binding and EventReporting Function BBERF, the Policy and Charging Rules Function PCRF,the Application Function AF, the Online Charging System OCS, the OfflineCharging System OFCS and the Subscription Profile Repository SPR or theUser Data Repository UDR.

The PCC architecture extends the architecture of an IP ConnectivityAccess Network IP-CAN, e.g. GPRS, where the PCEF is a functional entityin the gateway node implementing the IP access to the Packet DataNetwork PDN.

The PCRF is the part of the network architecture that aggregatesinformation to and from the network supporting the creation of rules andthen making policy decisions for subscribers active on the network.

In the mobile networks it is becoming more and more common that alsomachines as for example electricity meters and car supervision devicesare communicating with no or little human interaction. Communicationdevices in such machines will be more numerous than the devices used forhuman communication, and even though most of them may not generate a lotof traffic on a per device basis the sheer number of devices in acommunication network will generate a lot of traffic. Certain machines,for example surveillance cameras, may also send significant amount ofdata. Estimates indicate that within a few years the worldwide number ofcommunicating entities may reach 50 billion devices.

Although the use and advantage for society of such massive communicationcapability as utilized by M2M traffic is ample the value of each singletransmission may be considered low. It is therefore essential thatavailable capacity of the communication network is utilized in anefficient manner. A drawback with policy control as specified by 3GPP TS23.203 is that the policy enforcement provided by the PCEF only servesto limit traffic throughput exceeding that imposed by the policy controlrules of the PCRF.

SUMMARY OF INVENTION

An object of the invention is to provide a method and apparatus forcontrolling data transmission in a communication system mitigating theproblem of that policy enforcement provided by the PCEF only serves tolimit traffic throughput exceeding that imposed by the policy controlrules of the PCRF.

One aspect of the invention relates to a method performed by a datatransmission control node in a communication system. The methodcomprises in receiving a request for a transmission rule for a device;determining a transmission impacting parameter for the device based oninformation received in the request and based on the transmissionimpacting parameter further determining a device transmission rulegoverning the data transmission by the device. A transmission ruledeployment message is transmitted to the device enabling the device togovern transmission in accordance with the device transmission rule.

It is an advantage of the invention that the transmission of atransmission rule deployment message to the device enables the device togovern transmission in accordance with the transmission rule therebyenabling the sending device to optimize its traffic since this willallow for a better performing network with higher utilization, and costeffective solutions for the connected devices and subscribers.

Another aspect of the invention relates to a transmission control nodeapparatus comprising a processor and a memory. The memory is storinginstructions that, when executed by the processor, cause the apparatusto receive a request for a transmission rule for a device and todetermine a transmission impacting parameter for the device based oninformation received in the request. Based on the determinedtransmission impacting parameter the memory further comprisesinstruction that when executed by the processor cause the apparatus todetermine a device transmission rule governing the data transmission bythe device and to transmit a transmission rule deployment message to thedevice enabling the device to govern transmission in accordance with thedevice transmission rule.

A further aspect of the invention relates to a user equipment devicecomprising a processor and a memory. The memory is storing instructionsthat, when executed by the processor, cause the user equipment device toreceive a transmission rule deployment message to set a devicetransmission rule at the user equipment device, to collect data to betransmitted and to check the data for compliance with the devicetransmission rule. If affirmative the device transmits the data to aserver via a connectivity access network.

Embodiments of the invention will now be described in more detail withreference to the enclosed drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram showing a basic network structure fortransmission control in a communication system.

FIG. 2 is a block diagram showing the function blocks of a transmissioncontrol node.

FIG. 3 is a message sequence chart showing a method for control of datatransmission in a communication system.

FIG. 4 is a flow chart showing a method for controlling datatransmission in a transmission control node.

FIG. 5 is a block diagram showing an exemplary computing device forimplementing a system for controlling data transmission in acommunication system, or a user equipment device.

DETAILED DESCRIPTION OF THE INVENTION

The following detailed description of the exemplary embodiments refersto the accompanying drawings. The same reference numbers in differentdrawings identify the same or similar elements. Also, the followingdetailed description does not limit the invention. Instead, the scope ofthe invention is defined by the appended claims.

FIG. 1 is a block diagram showing the basic network structure oftransmission control node in a communication system.

The communication system 100 may be any type of communication systemcapable of transmitting data, for example a mobile communication systemsuch as Global System for Mobile communications (GSM), Wideband CodeDivision Multiple Access (WCDMA), General Packet Radio Service (GPRS),Enhanced Data rates for GSM Evolution (EDGE), High Speed Packet Access(HSPA) or Long Term Evolution (LTE) system. The invention is inparticular suitable for usage where machines communicate with each otherwithout continuous human interaction, so called machine-to-machine, orM2M, communication.

FIG. 1 shows a User Equipment (UE) device 110 such as a mobiletelephone, a machine-to-machine (M2M) communication device, a personaldigital assistant (PDA), personal computer or other type of computerwhich is provided access to a remote server 120 located at a Packet DataNetwork PDN 130 via an Internet Protocol (IP) Connectivity AccessNetwork (IP-CAN) 140, e.g. GPRS and a gateway (GW) 150, e.g. a GPRSGateway Support Node (GGSN).

By way of example, a device for M2M connectivity may be for example amobile telephone with limited display and keypad functionality butincluding a Device Data Collector (DDC) component 112 for collectingdata to be transmitted for further processing e.g. the metering part inthe electricity metering device. The collected data may also includevarious kinds of sensor data such as temperature, humidity, soundpressure but may also include data received from connected computerdevices. The device further includes a Device Data Transmitter (DDT)component 114 enabling access to the IP-CAN using for exampleGSM/WCDMA/GPRS/EDGE/HSPA or LTE. In an M2M context the UE controls itstransmission of data without direct control from a human user, i.e. onlyindirect usage control like usage of the service the device provides.The Data Transmitter is controlled by a Device Controller (DC) 116 thatbased on device transmission rules controls when the UE may transmitdata. In a similar manner, any type of UE device may be provided with aDC for controlling the transmission by a DDT.

The communication system includes a Transmission Control Node (TCN) 160for controlling data transmission in the communication system. Thetransmitted data may use any bearer such as GPRS, UnstructuredSupplementary Service Data (USSD) or Short Message Service (SMS).

The TCN includes a Transmission Controller (TC) 165 handling interactionwith the UEs for determining and setting rules for when a particular UEis allowed to transmit data. The rules are determined based on inputfrom a Transmission Environment Predictor TEP 170 providing variouscharacterizing transmission impacting parameters of the present as wellas forecasted environment in which transmission might occur.Characteristics includes present and forecasted network usagecharacteristics such as traffic load in various nodes of thecommunication system 100 provided by a Network Load Predictor (NLP) 172and cost characteristics such as price data for different types oftraffic in different parts of the communication system provided by aTransmission Cost Predictor (TCP) 174.

The NLP 172 makes predictions of the network load. The network load maybe location dependent and therefore needs to take into consideration thelocation of the UEs and the amount of data they will transmit. Thenetwork load also depends on other external factors, in addition to theimpact of devices controlled by the transmission control, like eventssuch as traffic stockings or football matches that needs to be known bythe TC in order to make the correct determinations.

The TCP 174 makes predictions of the cost for the transmission. Sincethe transmission cost may dependent on the network load, the TCP mayinteract with the NLP to take this into consideration. The costprediction provided to the TC by the TCP may be used to influence thetransmission control, having for example the UEs to transmit at thelowest possible cost. The TC 165 will control how data will be sent andthis will in turn influence the predicted cost, especially if the amountof transmission controlled devices constitutes a significant part of thetotal traffic in the communication network. The transmission control istherefore an iterative process. The UE may also subscribe to the presentcost from the TCN appended as a dynamic part to the device transmissionrule transmitted to the UE.

A Transmission Pattern and Rule Repository (TPRR) 180 is provided in theTCN used to store device transmission patterns describing thecharacteristics of how a device transmits its information to the serveror other connected devices. A device transmission pattern is identifiedby a device transmission pattern name and is described by for examplethe following parameters:

-   -   service; type of service (e.g. voice, data, SMS)    -   volume; volume of service that is transmitted each time    -   frequency; how often does the device transmit (including how        retransmission is handled)    -   criticality; how time critical is the transmission    -   mobility; how mobile is the device i.e. can the device change        location    -   QoS; what requirements does the device have on the Quality of        Service (QoS) of the transmission (e.g. data speed)

An example of a transmission pattern is: Service=Data, Volume=1 KB pertransmission, Frequency=Once per 24 h, Criticality=Minimum 1transmission per day, Mobility=Fixed, QoS=None.

The TPRR also stores device transmission rules that UEs needs to enforcefor when it is allowed to transmit. A device transmission rule isidentified by a device transmission rule name and is described by forexample the following parameters:

-   -   spatial; sets the area boundaries for the transmission    -   time; sets absolute time boundaries for the transmission    -   service; defines which service the rule is applicable for    -   volume; sets a cap on how much data that may be transmitted for        the rule    -   duration; sets the time window is for how long the transmission        can be    -   cost; indicates the maximum cost for the transmission expressed        in monetary value per byte

The device transmission rules may be overridden by a device requiringtransmission outside the rule boundaries, depending on for examplecriticality and for how long time a device can store events.

An example of a rule could be: Allowed transmission: Spatial=CellId1,Time=02:00-03:00, Service=Data, Volume=1 GB.

Further, a Device Repository (DR) 185 is provided in the TCN used tostore the present device transmission rules that a specific UE needs toenforce for when it is allowed to transmit as well as the devicetransmission pattern. Any UE or subscription identity such asInternational Mobile Subscriber Identity (IMSI), Mobile Subscriber ISDNNumber (MSISDN), Session Initiated Protocol—Uniform Resource Locator(SIP-URI), or IP address may be used to associate the UE with atransmission rule and a transmission pattern.

An Interface Unit (IU) 190 is provided in order to receive informationabout new devices and their transmission patterns via the gateway and totransmit a transmission rule deployment message to the UE via thegateway enabling the UE to govern transmission in accordance with thetransmission rule.

FIG. 2 is a block diagram showing the function blocks of a transmissioncontrol node.

The transmission control node 160 includes the TC 165 being connected toa database 240 including the TPRR 180 and the DR 185. Using for examplethe MSISDN=123456789 as lookup key the TC may access DR and determiningthat the present rule for the UE is <Rule 2> and the transmissionpattern of the UE is <HDCAMSURV>. By accessing the TPRR the TC obtainsthat the <HDCAMSURV> pattern indicates a high definition surveillancecamera having the characteristics Service=Video, Volume=500 KB pertransmission, Frequency=Occasionally, Criticality=Maximum 5 transmissionper day, Mobility=Fixed, QoS=High. The designation of Rule 2 may referto e.g. the definition: Spatial=CellId456, Time=00:00-23:59,Service=Data, Volume=2 GB.

The TC is operationally connected to the NLP 172 enabling it to retrievenetwork load predictions. Depending on network considerations the loadpredictions can refer to the particular cell or area where the UE islocated or may refer to the general load in the communication network.For example, in the cell where the UE is located the NLP may determinethe predicted load level for data transmission as e.g.(time_(—)00-06=LOW_TRAFFIC|time_06-18=HIGH_TRAFFIC|time_(—)18-00=MID_TRAFFIC).

The TC is also operationally connected to the TCP 174 enabling it toretrieve transmission cost predictions. For example, using theMSISDN=123456789, the TCP may determine the cost predictions for datatransmission for the particular subscriber. The transmission cost can bein monetary form e.g.(time_00-06=0.1$/MB|time_06-18=1.0$/MB|time_18-00=0.5$/MB or in relativeform, e.g. (time_00-06=LOW|time_06-18=HIGH|time_18-00=MID).

The NLP is further operationally connected to the TCP for two waypredictions retrieval. This is due to the fact that network operatorsoften strives to even out traffic in the network by steering traffictowards low traffic hours using cost as the steering means. Thus,network load as obtained from the NLP may be used to determine costlevels by the TCP—and cost levels from the TCP may be used by the NLP topredict network load. Therefore, cost prediction as well as loadprediction is an iterative process in that these factors are mutuallyaffecting each other.

The TC 165 includes a Determination Unit DU 210 used to determine therule to be applied by the device. A decision structure 220, for examplea decision tree, is traversed using transmission impacting parameterssuch as transmission pattern, network load prediction and/ortransmission cost prediction as modifiers in the structure in order tolocate the relevant device transmission rule to be applied. In theexample decision structure shown as a tree in FIG. 2, the transmissionpattern identifier HDSURVCAM for MSISDN=123456789 will locate therelevant modifier for branching into subpart of a decision tree. As anexample, provided present time is 03:00 the next lower modifier levelthe network load level being “LOW” is used to further branch into thefurther lower cost level modifier where the cost level being “LOW”finally determines that transmission rule “Rule 1” should be applied.

FIG. 3 is a message sequence chart showing a method for control of datatransmission in a communication system.

The method starts in when a new device is added to the network. TheTransmission Control gets in step 310 a new device notification messagefor a new device received from a device or from another source such as adevice management system. In the notification message the device informsthe TC either about its device transmission pattern or about the type ofdevice.

The new device notification message can be initiated manual e.g. when anew device is to be provisioned into the network it is provisioned alsoin the DR and TPRR. It can also be initiated automatic e.g. triggered bythe device itself or by the device management system.

The TC updates the TPRR and DR with one or plural add device messages instep 315. In the case the new device message included a devicetransmission pattern for the device the DR is updated accordingly. Inthe case only a type of device can be identified from the new devicenotification message, a database (not shown) is accessed by the TC forlooking up the pattern relevant for the device type. In case the newdevice notification message included a new device transmission patternnot already stored in the TPRR, TPRR is updated accordingly.

Step 310 and step 315 may occur for a plurality of devices. The newdevice initiation message and the add device message may also be batchmessages performing the update for a plurality of devices.

In step 318 a device transmission rule update procedure is triggered.The procedure is triggered by from the TCP, NLP or at time intervals.The Transmission Controller determines if there is a need to update thecurrent rules based on received:

-   -   a. Triggers from Transmission Cost Predictor based on that the        cost for data is e.g. high or low at the moment.    -   b. Triggers from the Network Load Predictor based on e.g. that        load due to usage in a certain location is either high or low at        the moment.    -   c. Triggers by set time intervals

Once triggered, the device transmission rule update procedure starts instep 320 as further detailed by the sub steps 322, 325 and 328 byretrieving transmission impacting parameters. The TC retrieves thecurrent transmission patterns and rules for a certain device, group ofdevices or type of devices from the TPRR and DR in step 322. In step 325the Transmission Controller retrieves the current network loadprediction. The current transmission cost prediction is retrieved by theTransmission Controller in step 328.

Once the Transmission Control has retrieved the transmission impactingparameters needed it evaluates the information and determines new rulesin step 330.

In step 335 it is determined if the rules have changed for the device.If that is the case, the TC deploys the device with the new devicetransmission rule for transmission control by the device by sending aset new rule message in step 340 causing the rule to be set in step 352.The DR is also updated with the new rule for the device in step 350 bysending a store rules message.

Information data is collected by the device data transmitter of thedevice in step 355 and depending on device type and device logic thedevice will order a transmission of the information data to the server.In step 360 the data that is to be sent is analyzed according to thetransmission rule check to check if it is possible to send the data incompliance with the device transmission rule. To do this, parameterssuch as time, geographical position and data volume is checked inaccordance with the rule. In certain situations however, for example ifthe device is running out of storage or the information time iscritical, device transmission rules may be overridden or thetransmission rule check omitted due to the priority of such situation.

If it is decided that the data should be transmitted the device datatransmitter that handles the actual transmission will receive the datafor transmission and transmit the data in step 365.

FIG. 4 is a flow chart showing a method for controlling datatransmission in a transmission control node.

The method is executed by a transmission control node TCN forcontrolling data transmission, for example SMS, USSD, GPRS data etc.Initially the TCN is in a waiting state 200. The TCN leaves the waitingstate in step 410 when it receives a new device notification message. Instep 415 the device's transmission pattern is added to the DR andoptionally the pattern is stored in the TPRR if not already existing,after which the TCN returns to the waiting state 200.

The TCN may also leave the waiting state 200 subsequent to receiving arequest for a transmission rule for a device triggering a transmissionrule update in a step 418 for example due to a determination that thetransmission cost and/or the determined network load have reached athreshold value. Thus, the request for a transmission rule for a devicemay be any one of the sub types timer trigger 418 a indicating a certaintime interval has lapsed, a network load trigger 418 b indicatingnetwork load in a certain location is high or low at the moment or atransmission cost trigger 418 c indicating that cost for datatransmission is high or low at the moment. E.g. for timer trigger, atcertain intervals that could be preconfigured (or due to other triggers)the entity handling transmission control update the transmission rulesat the device.

In step 420 one or several transmission impacting parameter aredetermined for the device based on information received in the request.The determination may be done by retrieving one or more of the currenttransmission patterns and/or rules for a certain device, group ofdevices or type of devices from the TPRR and DR in a sub step 422. Theretrieval may be made by accessing a device type identifier included inthe request and using the device type identifier to identify anassociated device transmission pattern. The determination may also bemade by accessing a device transmission pattern included in the request410. If not already existing, the transmission pattern is added to theTPRR. The device transmission pattern may be described by any one of ora combination of service-, volume-, frequency-, criticality-, mobility-or quality of service-parameters. Alternatively or in addition, the TCNmay retrieve the network load level as a present level or/and as aprediction from the NLP in a sub step 425. As a further alternatively orin addition, the transmission cost as a present level or/and as aprediction may be retrieved from the TCP in a sub step 428.

In step 430 a device transmission rule to govern the data transmissionfurther based on the transmission impacting parameter or parametersis/are determined, e.g. based on the devise transmission patterns,network load prediction and a transmission cost prediction.

The transmission rule may be characterized by any or a combination ofspatial-, time-, service-, volume-, duration-, and cost-parameters.

A determination is made in step 435 determining whether the determineddevice transmission rule differs from a presently deployed rule suchthat the device rule needs to be changed. Upon positive determination atransmission rule deployment message is transmitted to the device instep 440 enabling the device to govern transmission in accordance withthe transmission rule. The deployment message may include the completerule or it may send an identifier to a rule already accessible by thedevice.

In addition to deploying the device rule to the device, the rule mayalso be transmitted to the DR in step 250 for keeping track in the TCNof the present rules deployed in the device.

FIG. 5 is a block diagram showing exemplary embodiments of aTransmission Control Node apparatus TCN for controlling datatransmission in a communication system in the form of computing systemenvironment 500, and a user equipment device. As would be obvious toskilled person, the computing computing system environment 500represents a general platform that may be instantiated to serve variousfunctions. Thus, in FIG. 5 the function block relating to a TCN isreferenced with “N” while for a user equipment device the relatedfunction block may instead be those referenced as “D”.

Although as made clear above, the computing system environment 500 isonly one example of a suitable computing environment for a TCN or a userequipment device and is not intended to suggest any limitation as to thescope of use or functionality of the claimed subject matter. Further,the computing environment 500 is not intended to suggest any dependencyor requirement relating to the claimed subject matter and any one orcombination of components illustrated in the example operatingenvironment 500.

An example of a device for implementing the previously describedinnovation includes a general purpose computing device in the form of acomputer 510. Components of computer 510 can include, but are notlimited to, a processing unit 520, a system memory 530, and a system bus521 that couples various system components including the system memoryto the processing unit 520. The system bus 521 can be any of severaltypes of bus structures including a memory bus or memory controller, aperipheral bus, and a local bus using any of a variety of busarchitectures.

Computer 510 can include a variety of computer readable media. Computerreadable media can be any available media that can be accessed bycomputer 510. By way of example, and not limitation, computer readablemedia can comprise computer storage media and communication media.Computer storage media includes volatile and nonvolatile as well asremovable and non-removable media implemented in any method ortechnology for storage of information such as computer readableinstructions, data structures, program modules or other data. Computerstorage media includes, but is not limited to, RAM, ROM, EEPROM, flashmemory or other memory technology, CDROM, digital versatile disks (DVD)or other optical disk storage, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, or any othermedium which can be used to store the desired information and which canbe accessed by computer 510. Communication media can embody computerreadable instructions, data structures, program modules or other data ina modulated data signal such as a carrier wave or other transportmechanism and can include any suitable information delivery media.

The system memory 530 can include computer storage media in the form ofvolatile and/or nonvolatile memory such as read only memory (ROM) and/orrandom access memory (RAM). A basic input/output system (BIOS),containing the basic routines that help to transfer information betweenelements within computer 510, such as during start-up, can be stored inmemory 530. Memory 530 can also contain data and/or program modules thatare immediately accessible to and/or presently being operated on byprocessing unit 520. By way of non-limiting example, memory 530 can alsoinclude an operating system, application programs, other programmodules, and program data.

In some embodiments at least one of the TC 165, TEP 170, TPRR 180, DR185 and IU 190 function blocks may be implemented as software modulesloaded into the memory 530 and processable by the processing unit 520.In such embodiments the memory is storing instructions that, whenexecuted by the processor, cause the apparatus to receive a request fora transmission rule for a device and to determine a transmissionimpacting parameter for the device based on information received in therequest. Based on the determined transmission impacting parameter thememory further comprises instruction that when executed by the processorcause the apparatus to determine a device transmission rule governingthe data transmission by the device and to transmit a transmission ruledeployment message to the device enabling the device to governtransmission in accordance with the device transmission rule.

The computer 510 can also include other removable/non-removable andvolatile/nonvolatile computer storage media. For example, computer 510can include a hard disk drive that reads from or writes tonon-removable, nonvolatile magnetic media, a magnetic disk drive thatreads from or writes to a removable, nonvolatile magnetic disk, and/oran optical disk drive that reads from or writes to a removable,nonvolatile optical disk, such as a CD-ROM or other optical media. Otherremovable/non-removable, volatile/nonvolatile computer storage mediathat can be used in the exemplary operating environment include, but arenot limited to, magnetic tape cassettes, flash memory cards, digitalversatile disks, digital video tape, solid state RAM, solid state ROMand the like. A hard disk drive can be connected to the system bus 521through a non-removable memory interface such as an interface, and amagnetic disk drive or optical disk drive can be connected to the systembus 521 by a removable memory interface, such as an interface.

A user can enter commands and information into the computer 510 throughinput devices such as a keyboard or a pointing device such as a mouse,trackball, touch pad, and/or other pointing device. Other input devicescan include a microphone, joystick, game pad, satellite dish, scanner,or similar devices. These and/or other input devices can be connected tothe processing unit 520 through user input 540 and associatedinterface(s) that are coupled to the system bus 521, but can beconnected by other interface and bus structures, such as a parallelport, game port or a universal serial bus (USB).

A graphics subsystem can also be connected to the system bus 521. Inaddition, a monitor or other type of display device can be connected tothe system bus 521 through an interface, such as output interface 550,which can in turn communicate with video memory. In addition to amonitor, computers can also include other peripheral output devices,such as speakers and/or printing devices, which can also be connectedthrough output interface 550.

The computer 510 can operate in a networked or distributed environmentusing logical connections to one or more other remote computers, such asremote server 570, which can in turn have media capabilities differentfrom device 510. The remote server 570 can be a personal computer, aserver, a router, a network PC, a peer device or other common networknode, and/or any other remote media consumption or transmission device,and can include any or all of the elements described above relative tothe computer 510. The logical connections depicted in FIG. 5 include anetwork 571, such as a local area network (LAN) or a wide area network(WAN), but can also include other networks/buses.

When used in a LAN networking environment, the computer 510 is connectedto the LAN 571 through a network interface or adapter. When used in aWAN networking environment, the computer 510 can include acommunications component, such as a modem, or other means forestablishing communications over a WAN, such as the Internet. Acommunications component, such as a modem, which can be internal orexternal, can be connected to the system bus 521 through the user inputinterface at input 540 and/or other appropriate mechanism.

In a networked environment, program modules depicted relative to thecomputer 510, or portions thereof, can be stored in a remote memorystorage device. It should be noted that the network connections shownand described are exemplary and other means of establishing acommunications link between the computers can be used.

Additionally, it should be noted that as used in this application, termssuch as “component,” “display,” “interface,” and other similar terms areintended to refer to a computing device, either hardware, a combinationof hardware and software, software, or software in execution as appliedto a computing device. For example, a component may be, but is notlimited to being, a process running on a processor, a processor, anobject, an executable, a thread of execution, a program and a computingdevice. As an example, both an application running on a computing deviceand the computing device can be components. One or more components canreside within a process and/or thread of execution and a component canbe localized on one computing device and/or distributed between two ormore computing devices, and/or communicatively connected modules.Further, it should be noted that as used in this application, terms suchas “system user,” “user,” and similar terms are intended to refer to theperson operating the computing device referenced above.

As with the TCN, a computing system such as the computing system 500described in FIG. 5 may, as have been described in the foregoing, alsobe adapted to perform the functions of a user equipment device. In suchembodiment the function blocks DCC 112, DDT 114 and DC 116 are softwaremodules loaded into the memory and processable by the processing unitadapting the user equipment device to receive a transmission ruledeployment message to set a device transmission rule at the userequipment device, to collect data to be transmitted and to check thedata for compliance with the device transmission rule. If affirmativethe device transmits the data to a server via a connectivity accessnetwork.

When an element is referred to as being “connected”, “coupled”,“responsive”, or variants thereof to another element, it can be directlyconnected, coupled, or responsive to the other element or interveningelements may be present. In contrast, when an element is referred to asbeing “directly connected”, “directly coupled”, “directly responsive”,or variants thereof to another element, there are no interveningelements present. Like numbers refer to like elements throughout.Furthermore, “coupled”, “connected”, “responsive”, or variants thereofas used herein may include wirelessly coupled, connected, or responsive.As used herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. Well-known functions or constructions may not be described indetail for brevity and/or clarity. The term “and/or” includes any andall combinations of one or more of the associated listed items.

As used herein, the terms “comprise”, “comprising”, “comprises”,“include”, “including”, “includes”, “have”, “has”, “having”, or variantsthereof are open-ended, and include one or more stated features,integers, elements, steps, components or functions but does not precludethe presence or addition of one or more other features, integers,elements, steps, components, functions or groups thereof. Furthermore,as used herein, the common abbreviation “e.g.”, which derives from theLatin phrase “exempli gratia,” may be used to introduce or specify ageneral example or examples of a previously mentioned item, and is notintended to be limiting of such item. The common abbreviation “i.e.”,which derives from the Latin phrase “id est,” may be used to specify aparticular item from a more general recitation.

It should also be noted that in some alternate implementations, thefunctions/acts noted in the blocks may occur out of the order noted inthe flowcharts. For example, two blocks shown in succession may in factbe executed substantially concurrently or the blocks may sometimes beexecuted in the reverse order, depending upon the functionality/actsinvolved. Moreover, the functionality of a given block of the flowchartsand/or block diagrams may be separated into multiple blocks and/or thefunctionality of two or more blocks of the flowcharts and/or blockdiagrams may be at least partially integrated.

Finally, other blocks may be added/inserted between the blocks that areillustrated. Moreover, although some of the diagrams include arrows oncommunication paths to show a primary direction of communication, it isto be understood that communication may occur in the opposite directionto the depicted arrows.

Many different embodiments have been disclosed herein, in connectionwith the above description and the drawings. It will be understood thatit would be unduly repetitious and obfuscating to literally describe andillustrate every combination and subcombination of these embodiments.Accordingly, the present specification, including the drawings, shall beconstrued to constitute a complete written description of variousexemplary combinations and subcombinations of embodiments and of themanner and process of making and using them, and shall support claims toany such combination or subcombination.

Many variations and modifications can be made to the embodiments withoutsubstantially departing from the principles of the present invention.All such variations and modifications are intended to be included hereinwithin the scope of the present invention.

1-19. (canceled)
 20. A method performed by a data transmission control node in a communication system, comprising the steps of: receiving a request for a transmission rule for a device; determining a transmission impacting parameter for the device based on information received in the request; based on the transmission impacting parameter further determining a device transmission rule governing data transmission by the device; and transmitting a transmission rule deployment message to the device, enabling the device to govern data transmission in accordance with the device transmission rule.
 21. The method according to claim 20, wherein the step of determining the transmission impacting parameter includes the further step of determining a device transmission pattern.
 22. The method according to claim 21, wherein the further step of determining the device transmission pattern comprises: accessing a device type identifier included in the request; and using the device type identifier to identify an associated device transmission pattern.
 23. The method according to claim 21, wherein the step of determining the device transmission pattern comprises accessing a device transmission pattern included in the request.
 24. The method according to claim 23, further comprising adding the device transmission pattern to a device transmission pattern repository.
 25. The method according to claim 21, wherein the device transmission pattern is defined by any one of or a combination of service-, volume-, frequency-, criticality-, mobility- or quality-of-service-parameters.
 26. The method according to claim 20, wherein the step of determining the transmission impacting parameter is based on determining a communication network load level.
 27. The method according to claim 20, wherein the step of determining the transmission impacting parameter is based on determining a communication network transmission cost.
 28. The method according to claim 20, wherein the step of determining the device transmission rule and the step of transmitting the transmission rule deployment message are initiated by the transmission control node upon determining that at least one of a transmission cost and a network load has reached a corresponding threshold value.
 29. The method according to claim 20, wherein the step of determining the device transmission rule and the step of transmitting the transmission rule deployment message are repeated at predetermined intervals.
 30. The method according to claim 20, wherein, before the step of transmitting the transmission rule deployment message, the method includes determining whether the determined device transmission rule differs from a presently deployed device transmission rule and transmitting the transmission rule deployment message only upon a positive determination.
 31. The method according to claim 30, further comprising, upon the positive determination, transmitting the transmission rule deployment message to a transmission pattern repository.
 32. The method according to claim 20, wherein the device transmission rule is comprised by any or a combination of spatial-, time-, service-, volume-, duration-, and cost-parameters.
 33. The method according to claim 20, wherein the transmission rule deployment message comprises the data transmission rule or an identifier of the data transmission rule.
 34. A transmission control node apparatus comprising a processor, and a memory storing instructions that, when executed by the processor, configure the apparatus to: determine a transmission impacting parameter for a device based on information received in a request for a transmission rule for the device; determine a device transmission rule governing data transmission by said device, based on the determined transmission impacting parameter; and transmit a transmission rule deployment message to the device, thereby enabling the device to govern data transmission in accordance with the device transmission rule.
 35. The transmission control node apparatus according to claim 34, wherein the determination of the transmission impacting parameter is based on a determination of a device transmission pattern.
 36. The transmission control node apparatus according to claim 34, wherein the transmission rule deployment message comprises the device transmission rule or an identifier of the device transmission rule.
 37. A user equipment device comprising a processor, and a memory storing instructions that, when executed by the processor, configure the device to: set a device transmission rule at the user equipment device according to a transmission rule deployment message received by the user equipment device; collect data to be transmitted; check the data for compliance with the device transmission rule; and if said check is affirmative, transmit the data to a server via a connectivity access network.
 38. The user equipment device according to claim 37 wherein the transmission rule deployment message comprises the data transmission rule or an identifier of the data transmission rule. 